Skip to content

use rest api - #4

Merged
AashishChakravarty merged 2 commits into
mainfrom
rest-api
Oct 14, 2026
Merged

AashishChakravarty merged 2 commits into
mainfrom
rest-api

Conversation

@Abica

@Abica Abica commented Oct 14, 2026

Copy link
Copy Markdown
Member

No description provided.

Abica added 2 commits October 8, 2026 18:10
Each operation is now one request to a resource endpoint (answers,
transforms, memories, skill runs) with named fields in the response. The
node no longer names tools or reads a tool result envelope.

Slow work is followed through the task the API returns: the node asks
the server to hold the request with Prefer: wait, then polls the task's
location until the result is ready or Wait for Result runs out.

An unverified answer is data (verified: false) rather than a node
failure. Transform can split its result into one item per row. Memory
Name defaults to "default". OAuth2 credentials use the server-less
routes, since the token identifies the server.
An OAuth2 credential has no Server ID, so activating the trigger with
one failed. The trigger now asks the gateway which server the token
belongs to, and reads the credential again before dialling so the
socket gets a refreshed token.

Activation also switched on the JSON-RPC transport, which only the old
action node needed. It now enables WebSocket alone.

The activation steps move beside the socket session so they can be
tested without the n8n runtime.
@AashishChakravarty
AashishChakravarty merged commit d8b2abe into main Oct 14, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants